Device maintenance of a data storage device including wear levelling, garbage collection, or combination thereof

ABSTRACT

A system includes a data storage device and a host computing device. The data storage device includes a host interface; integrated circuit memory cells; and a processing device. The processing device is configured to execute firmware to perform operations requested by commands received via the host interface and maintenance operations identified by the processing device independent of commands received via the host interface. The host computing device is coupled to the host interface to provide commands with addresses to access the integrated circuit memory cells according to the address. In response to a request, the host computing device is configured to reduce, to below a threshold, a rate of transmitting to the host interface commands to access integrated circuit memory cells; and power up the data storage device to cause the data storage device to perform the maintenance operations.

FIELD OF THE TECHNOLOGY

At least some embodiments disclosed herein relate generally to data storage devices and, more particularly, to maintaining data storage devices.

BACKGROUND

Data storage devices can operate less than optimally during field usage, such as when used in a vehicle (e.g., automobile or the like). Typically, the data storage device may not be given an opportunity to perform routine maintenance operations such as defragmentation, trimming, refreshing, wear levelling, garbage collection, combinations thereof, and the like. This can be, for example, because the data storage device does not receive enough time to complete the maintenance operations without receiving commands to access memory cells.

Improved maintenance of data storage devices is desirable.

BRIEF DESCRIPTION OF THE DRAWINGS

References are made to the accompanying drawings that form a part of this disclosure and illustrate embodiments in which the systems and methods described in this Specification can be practiced.

FIG. 1 is a schematic block diagram of a vehicle having computing devices connected via a communications bus, according to an embodiment

FIG. 2 is a block diagram of the data storage device of FIG. 1, according to an embodiment.

FIG. 3 shows a flowchart illustrating a method for maintaining a data storage device, according to an embodiment.

FIG. 4 shows a flowchart illustrating a method for maintaining a data storage device, according to an embodiment.

Like reference numbers represent like parts throughout.

DETAILED DESCRIPTION

Data storage devices can be used in a variety of applications such as, but not limited to, on board vehicles (e.g., automobiles). The data storage devices can be used for various vehicle systems including, but not limited to, the engine, the infotainment system, as a data recorder, combinations thereof, or the like.

Generally, a processing device of the data storage device may not have enough processing power to perform operations such as read and write operations to specific memory cells and concurrently to perform typical maintenance operations such as, but not limited to, defragging, refreshing, wear levelling optimization, and suitable combinations thereof. The maintenance operations are generally prioritized at a relatively lower priority than the read and write operations of the data storage device. In some instances, the maintenance operations are limited to being performed when the read and write requests are received below a threshold request rate. As a result, the maintenance operations may not be performed, and the data storage device may operate in a less than optimal state over time.

The methods, devices, and systems described in this disclosure enable a renewal mode in which the maintenance operations are performed for data storage devices. The renewal mode may be initiated by, for example, a service technician (e.g., at a repair facility) at a time in which the read and write requests of the data storage device are not critical (e.g., when the vehicle is parked for maintenance). During the renewal mode, a host computing device may reduce (or stop altogether) the read and write requests. In an embodiment, the data storage device may reprioritize the maintenance operations such that the maintenance operations have a relatively higher priority than the read and write requests.

In an embodiment, when the host computing device is communicatively coupled to a network, the renewal mode can also include a firmware update for the data storage device.

The embodiments described in this Specification can, for example, result in a data storage device that has an improved lifetime before failure, especially in an automotive application.

A system includes a data storage device and a host computing device. The data storage device includes a host interface; integrated circuit memory cells; and a processing device. The processing device is configured to execute firmware to perform operations requested by commands received via the host interface and maintenance operations identified by the processing device independent of commands received via the host interface. The host computing device is coupled to the host interface to provide commands with addresses to access the integrated circuit memory cells according to the address. In response to a request, the host computing device is configured to reduce, to below a threshold, a rate of transmitting to the host interface commands to access integrated circuit memory cells; and power up the data storage device to cause the data storage device to perform the maintenance operations.

A data storage device is also disclosed. The data storage device includes a host interface communicatively coupled to a host computing device; integrated circuit memory cells; and a processing device. The processing device is configured to execute firmware to perform operations requested by commands received via the host interface and maintenance operations identified by the processing device independent of commands received via the host interface. In response to a request received in the host interface to enter a renewal mode, the processing device is configured via the firmware to reprioritize the maintenance operations to a relatively higher priority than operations requested by host commands received in the host interface from the host computing device. The processing device is also configured to perform one or more of the maintenance operations.

A method implemented in a vehicle is also disclosed. The method includes, in response to a request from a host computing device to enter a renewal mode, reducing, to below a threshold, a rate of transmitting from the host computing device to a host interface of a data storage device commands to access integrated circuit memory cells of the data storage device. The method further includes powering the data storage device to cause the data storage device to execute firmware to perform maintenance operations identified by a processing device of the data storage device that are independent of the commands received via the host interface to access the integrated circuit memory cells.

The data storage device and host computing device are described in additional detail in accordance with an implementation in a vehicle. It is to be appreciated that the systems and methods described are applicable in systems other than a vehicle in accordance with the principles described.

FIG. 1 is a schematic block diagram of a vehicle 100 having computing devices connected via a communications bus 105, according to an embodiment. The computing devices include at least a host computing device 110 and a data storage device 115, according to an embodiment. In an embodiment the vehicle 100 is an automobile and can, for example, be an autonomous vehicle, a semiautonomous vehicle, or the like.

The host computing device 110 may be representative of, for example, various computing devices in the vehicle 100. For example, the host computing device 110 can be an infotainment system; a black box data recorder; an advanced driver assistance system (ADAS); an engine controller; a camera system; a storage service; suitable combinations thereof, or the like.

The host computing device 110 is communicatively coupled to the data storage device 115 via the communications bus 105. The communications bus 105 can utilize a selected communication protocol such as, but not limited to, peripheral component interconnect (PCI); peripheral component interconnect express (PCIe); or the like.

In the illustrated embodiment, the vehicle 100 further includes sensors 120. The host computing device 110 is communicatively coupled to the sensors 120. The sensors 120 are illustrated as being communicatively coupled to the host computing device 110 via the communications bus 105. In an embodiment, one or more of the sensors 120 can be communicatively coupled to the host computing device 110 via a wireless connection, or via a combination of a wireless connection and the wired connection of the communications bus 105.

The sensors 120 may be configured to collect information related to the operation of the vehicle 100. For example, the sensors 120 may be configured to collect information related to the speed, acceleration, deceleration, etc., of the vehicle 100. In an embodiment, the vehicle 100 may additionally include one or more actuators to, for example, exert control on at least a portion of the vehicle 100 in response to one or more values received from the sensors 120. In an embodiment, the sensors 120 may be configured to stream sensed values to the data storage device 115 for storage.

The vehicle 100 can include additional features such as, a power source 125. In an embodiment, the power source 125 can be a battery that is electrically connected to the host computing device 110 and to the data storage device 115. It is to be appreciated that the vehicle 100 can include a variety of additional features.

FIG. 2 is a block diagram of the data storage device 115 of FIG. 1, according to an embodiment. In an embodiment, the data storage device 115 is a solid-state drive (SSD). In another embodiment, the data storage device 115 can be a hard disk drive (HDDs); flash memory; dynamic random-access memory (DRAM); magnetic tape; network attached storage device; or the like.

The data storage device 115 includes a host interface 130, a processing device 135, firmware 140, and storage media 145.

The host interface 130 is communicatively coupled to the communications bus 105 (FIG. 1). The host interface 130 can be, for example, in a form of a standardized interface such as, but not limited to, a serial advanced technology attachment (SATA); a universal serial bus (USB); a peripheral component interconnect express (PCIe); or the like. The host interface 130 communicates information between the host computing device 110 and the storage media 145.

The host interface 130 is responsible for passing control, access, data, and other signals between the data storage device 115 and the host computing device 110 (FIG. 1).

The processing device 135 runs firmware 140 to perform operations responsive to the communications from the host computing device 110. Firmware 140 includes, for example, a type of computer program that provides control, monitoring, and data manipulation of data storage devices. The firmware 140 controls operations of the processing device 135 in operating the data storage device 115, such as storing and accessing data in the storage media 145.

The firmware 140 can be configured to include instructions for performing maintenance operations such as when the data storage device is in a renewal mode. For example, the firmware 140 includes a sequence of maintenance operations such as, but not limited to, scan, defragmentation, trim, refresh, wear levelling, garbage collection, or any combination thereof. The sequence of the maintenance operations may be defined based on the type of storage media 145. For example, the sequence can vary depending upon whether the storage media includes single-layer cells (SLCs); multi-layer cells (MLCs); triple-layer cells (TLCs); or quad-layer cells (QLCs). The sequence of maintenance operations generally is not significant and can be varied. Additionally, one or more of the maintenance operations may not be included based on its effectiveness for the type of storage media 145. In an embodiment, the host computing device 110 may be connected to a network. In such an embodiment, the maintenance operations can include updating the firmware 140.

The maintenance operations defined in the firmware 140 can have a default priority when not in the renewal mode. The default priority for the maintenance operations can be relatively lower than operations requested by commands received via the host interface 130. That is, operations requested by commands received via the host interface 130, such as read, write, or combinations thereof, are typically higher priority relative to the maintenance operations. As a result, the maintenance operations may be infrequently performed, or sometimes not at all.

The renewal mode defined in the firmware 140 causes the maintenance operations to be prioritized above the operations requested by commands received via the host interface 130. In an embodiment, the renewal mode can be entered when the request rate of the operations requested by commands received via the host interface 130 is below a threshold value, or alternatively, when operations requested by commands received via the host interface 130 are stopped for a period of time.

At least a portion of the storage media 145 is non-volatile. That is, the storage media 145 does not require power to maintain the data or information stored in the storage media 145 and the data or information is retrievable after the storage media 145 is powered off and then powered on again. Memory cells 150 of the storage media 145 can be implemented using, for example, NAND gate-based flash memory; phase-change memory (PCM); magnetic memory (MRAM); resistive random-access memory; 3D XPoint; or the like. As a result, the storage media 145 is non-volatile and can retain data stored therein without power for days, months, or years. In an embodiment, the memory cells 150 can be single-layer cells (SLCs); multi-layer cells (MLCs); triple-layer cells (TLCs); quad-layer cells (QLCs); or the like.

The data storage device 115 may utilize volatile memory for the storage of run-time data and instructions used by the processing device 135. For example, volatile dynamic random-access memory (DRAM); volatile static random-access memory (SRAM); or the like can be used. The volatile memory requires power to maintain the data or information stored therein, and the data or information is rapidly or immediately lost when the power is interrupted. In an embodiment, the processing device 135 can alternatively or additionally include in-process cache memory.

In an embodiment, the processing device 135 can store performance data for the data storage device 115 in the storage media 145. In such an embodiment, the processing device 135 can monitor how the maintenance operations impact the overall performance of the data storage device 115. The performance data can then be used to, for example, determine an order for the maintenance operations in the firmware 140. In such an embodiment, the processing device 135 may selectively determine which of the maintenance operations to perform in the renewal mode based on an expected duration of the renewal mode, selecting the maintenance operations that have a relatively higher improvement in the performance of the data storage device 115 to be performed first.

A non-transitory computer-readable storage medium can be used to store instructions of the firmware 140. When the instructions are executed by the processing device 135, the instructions cause the processing device 135 to perform a method discussed in further detail below. In one example, the storage media 145 includes the non-transitory computer-readable storage medium storing the instructions of the firmware 140.

FIG. 3 shows a flowchart illustrating a method 200 for maintaining a data storage device, according to an embodiment. For example, the method 200 can be implemented in the vehicle 100 of FIG. 1 having host computing device 110 and data storage device 115 as shown in FIGS. 1 and 2.

The method 200 of FIG. 3 includes determining by the host computing device 110 whether a request to enter a renewal mode has been received at block 205. The request can be a dealer service command generated by, for example, a service technician in a variety of ways. For example, the service technician can connect a service computer to the host computing device 110 and cause a dealer service command to be generated and sent from the service computer to the host computing device 110.

If no request has been received, the method includes streaming data from sensors 120 to the data storage device 115 at block 210. Block 210 may generally be representative of an ongoing or normal operation for the sensors 120. That is, the sensors 120 can generally be configured to stream data to the data storage device 115 when not in the renewal mode. In an embodiment, the sensors 120 may be configured to stream data from the sensors 120 to the data storage device 115. In another embodiment, the sensors 120 may be configured to stream data to the host computing device 110, which then sends the data to the data storage device 115.

In response to a request being received by the host computing device 110, the method 200 includes reducing a rate of transmitting commands from the host computing device 110 to access the storage media integrated circuit memory cells 150 to the host interface 130 to below a threshold at block 215. In an embodiment, reducing the rate of transmitting commands from the host computing device 110 to access the storage media integrated circuit memory cells 150 to the host interface 130 can include stopping the commands completely (e.g., a rate of 0).

Further, in response to receiving the request, the method 200 includes powering the data storage device 115 (e.g., via the power source 125) at block 220 to cause the data storage device 115 to perform the maintenance operations. Typically, when the data storage device 115 does not receive commands from the host computing device 110 to access the storage media integrated circuit memory cells 150, the data storage device 115 is configured to enter a reduced power mode (e.g., a sleep or hibernate mode). The data storage device 115 may be configured (e.g., via firmware) to not perform maintenance operations if the data storage device 115 is in a reduced power mode. The powering of the data storage device 115 at block 220 can be performed to prevent the data storage device 115 from entering the reduced power mode, or if already in the reduced power mode, to enter a full power mode.

In an embodiment, the powering at block 220 may include the host computing device 110 sending a signal to the data storage device 115 that prevents the data storage device 115 from entering the reduced power mode. In an embodiment, the data storage device 115 is in a full power mode and block 220 prevents the data storage device 115 from switching to the reduced power mode. In an embodiment, if the data storage device 115 was previously in the reduced power mode, block 220 can include sending a signal from the host computing device to the data storage device 115 to enter the full power mode and maintain the full power mode during the renewal mode. Thus, block 220 can prevent the power from being removed from the data storage device 115 during the renewal mode. When the data storage device 115 receives the signal to enter the full power mode and is not receiving requests, the maintenance operations are triggered.

If the power is removed, or the maintenance operations are completed, the renewal mode may be exited. It is to be appreciated that in an embodiment, an explicit command to exit the renewal mode may be generated by the service technician. Upon exiting of the renewal mode, the rate of transmitting commands from the host computing device 110 to access the storage media integrated circuit memory cells 150 to the host interface 130 is no longer reduced (i.e., returned to a normal rate).

FIG. 4 shows a flowchart illustrating a method 250 for maintaining a data storage device, according to an embodiment. For example, the method 250 can be implemented in the data storage device 115 of FIG. 2.

The method 250 includes determining, by the processing device 135, whether a request to enter a renewal mode has been received via the host interface 130 at block 255. The request can be a dealer service command generated by, for example, a service technician in a variety of ways. For example, the service technician can connect a service computer to the host computing device 110 and cause a dealer service command to be generated and sent from the service computer to the host computing device 110.

If no request has been received via the host interface 130, the method 250 includes receiving data from the host computing device 110 or sensors 120 via the host interface 130 at block 260. Block 260 may generally be representative of an ongoing or normal operation for the sensors 120 or the host computing device 110. That is, the sensors 120, the host computing device 110, or combinations thereof, are generally configured to stream data to the data storage device 115 when not in the renewal mode.

In response to a request being received via the host interface 130, the method 250 includes reprioritizing, by the processing device 135, the maintenance operations to a relatively higher priority than operations requested by host commands received in the host interface 130 from the host computing device 110 at block 265. At block 265, the reprioritizing of the maintenance operations by the processing device 135 can be completed by increasing a priority of the maintenance operations to be relatively higher than the operations requested by the host commands received in the host interface 130 from the host computing device 110; preventing host commands at the host interface 130 for a period of time; decreasing a priority of the operations requested by the host commands received in the host interface 130 from the host computing device 110 to be relatively lower than the priority of the maintenance operations; or suitable combinations thereof.

One or more of the maintenance operations is performed by the processing device 135 at block 270.

Upon completion of the maintenance operations, the processing device 135 can be configured to exit the renewal mode. In an embodiment, the processing device 135 can be configured to exit the renewal mode in response to receiving a signal (e.g., from the host interface 130) indicative of a request to exit the renewal mode (e.g., as generated by a service technician). In response to receiving the signal indicative of the request to exit the renewal mode, the processing device 135 is configured to reprioritize the host commands to a relatively higher priority than the maintenance operations. That is, the processing device 135 is configured to return the maintenance operations to their default priority.

Although exemplary implementations of methods 300 and 400 are described above with reference to the components of the vehicle 100 and data storage device 115 of FIGS. 1 and 2, it should be recognized that such implementations are not limiting and that other implementations of methods 300 and 400 are within the scope of the present disclosure.

Examples of computer-readable storage media (e.g., non-transitory computer-readable storage media) include, but are not limited to, any tangible medium capable of storing a computer program for use by a programmable processing device to perform functions described herein by operating on input data and generating an output. A computer program is a set of instructions that can be used, directly or indirectly, in a computer system to perform a certain function or determine a certain result. Examples of computer-readable storage media include, but are not limited to, a floppy disk; a hard disk; a random access memory (RAM); a read-only memory (ROM); a semiconductor memory device such as, but not limited to, an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), Flash memory, or the like; a portable compact disk read-only memory (CD-ROM); an optical storage device; a magnetic storage device; other similar device; or suitable combinations of the foregoing.

In some embodiments, hardwired circuitry may be used in combination with software instructions. Thus, the description is not limited to any specific combination of hardware circuitry and software instructions, nor to any source for the instructions executed by the data processing system.

The terminology used herein is intended to describe embodiments and is not intended to be limiting. The terms “a,” “an,” and “the” include the plural forms as well, unless clearly indicated otherwise. The terms “comprises” and/or “comprising,” when used in this Specification, specify the presence of the stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, and/or components.

It is to be understood that changes may be made in detail, especially in matters of the construction materials employed and the shape, size, and arrangement of parts without departing from the scope of the present disclosure. This Specification and the embodiments described are examples, with the true scope and spirit of the disclosure being indicated by the claims that follow. 

What is claimed is:
 1. A system, comprising: a data storage device, including: a host interface; integrated circuit memory cells; and a processing device configured to execute firmware to perform: operations requested by commands received via the host interface; maintenance operations identified by the processing device independent of commands received via the host interface; and a host computing device coupled to the host interface to provide commands with addresses to access the integrated circuit memory cells according to the address; wherein in response to a first request, the host computing device is configured to: reduce, to below a threshold, a rate of transmitting to the host interface commands to access integrated circuit memory cells; and power up the data storage device to cause the data storage device to perform the maintenance operations; wherein in response to a second request or completion of the maintenance operations, the host computing device is configured to: prioritize the operations requested by commands received via the host interface over the maintenance operations.
 2. The system of claim 1, wherein the system is a vehicle.
 3. The system of claim 1, wherein the system includes sensors, and in absence of the request, the host computing device is configured to stream data from the sensors to the host interface.
 4. The system of claim 1, wherein the commands to access integrated circuit memory cells include read, write, or any combination thereof.
 5. The system of claim 1, wherein the maintenance operations include scan, defragmentation, trim, refresh, wear levelling, garbage collection, or any combination thereof.
 6. The system of claim 5, wherein in response to the host computing device receiving a signal indicative of a network connection, the maintenance operations further include a firmware update.
 7. The system of claim 1, wherein the processing device is further configured to stop the maintenance operations in response to receiving a signal indicative of the second request from the host device.
 8. The system of claim 6, wherein in response to receiving the signal indicative of the second request, the rate of transmitting to the host interface commands to access integrated circuit memory cells is returned to a normal rate.
 9. The system of claim 1, wherein the processing device is further configured to: monitor and store performance data of the data storage device in the integrated circuit memory cells; perform the maintenance operations; and measure a performance improvement of the data storage device after performance of the maintenance operations.
 10. The system of claim 9, wherein the processing device is further configured to: based on a predicted time the data storage device is expected to have the reduced rate of transmitting to the host interface the commands to access the integrated circuit memory cells, selectively perform the maintenance operations to maximize performance improvement based on the stored performance data.
 11. A data storage device, comprising: a host interface communicatively coupled to a host computing device; integrated circuit memory cells; and a processing device configured to execute firmware to perform: operations requested by commands received via the host interface; maintenance operations identified by the processing device independent of commands received via the host interface; and wherein, in response to a request received in the host interface to enter a renewal mode, the processing device is configured via the firmware to: reprioritize the maintenance operations to a relatively higher priority than operations requested by host commands received in the host interface from the host computing device; and perform one or more of the maintenance operations; wherein the processing device is further configured to exit the renewal mode in response to receiving a signal indicative of a request to exit the renewal mode; and wherein in response to receiving the signal indicative of the request to exit the renewal mode, the processing device is further configured to reprioritize the host commands to a relatively higher priority than the maintenance operations.
 12. The data storage device of claim 11, wherein reprioritizing the maintenance operation includes one of: increasing a priority of the maintenance operations; or decreasing a priority of the host commands.
 13. The data storage device of claim 11, wherein reprioritizing the maintenance operations includes blocking the host commands from the host computing device to the data storage device and preventing the data storage device from hibernating, wherein the data storage device is configured to perform maintenance operations when not hibernating and in absence of receiving host commands.
 14. The data storage device of claim 11, wherein the data storage device is a solid-state drive (SSD).
 15. The data storage device of claim 11, wherein the host computing device is an on-board computer of a vehicle.
 16. A method, comprising: in response to a request from a host computing device to enter a renewal mode, reducing, to below a threshold, a rate of transmitting from the host computing device to a host interface of a data storage device commands to access integrated circuit memory cells of the data storage device; and powering the data storage device to cause the data storage device to execute firmware to perform maintenance operations identified by a processing device of the data storage device that are independent of the commands received via the host interface to access the integrated circuit memory cells; in response to receiving a signal indicative of a request to exit the renewal mode, exiting the renewal mode, and reprioritizing the host commands to a relatively higher priority than the maintenance operations.
 17. The method of claim 16, wherein in absence of the request, the method further comprises streaming data from sensors of a vehicle to the host interface of the data storage device.
 18. The method of claim 16, wherein the maintenance operations include scan, defragmentation, trim, refresh, wear levelling, garbage collection, or any combination thereof. 